[6.x] Fix nav:breadcrumbs for multi-site#13789
Merged
Merged
Conversation
|
Any news on that one? This bug has quite an impact and its open since February. Are there any plans to merge this? |
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the issue
Using {{ nav:breadcrumbs }} on multi-site, it fails to generate links when Site URL is configured as:
{{ config:app:url }}/path/So for example you can go to collection route with parent and children like:
https://example.test/path/entry/child/sub-childIt generates just one link to "Home", no other links to navigate backwards.
What this PR Does
It generates the correct links now for all kind of site configs. It respects new enforceTrailingSlashes.
Related #11840